5.5
MEDIUM CVSS 3.1
CVE-2026-46170
mptcp: pm: ADD_ADDR rtx: free sk if last
Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: free sk if last When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end. If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put(). But that's not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on "itself".

INFO

Published Date :

May 28, 2026, 10:16 a.m.

Last Modified :

June 11, 2026, 12:19 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-46170 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Fix memory corruption by correctly managing socket references and timers.
  • Use sock_put() instead of __sock_put() for last references.
  • Mark timer as done if not rescheduled.
  • Avoid calling sk_stop_timer_sync() on the same timer.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-46170 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-46170 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-46170 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-46170 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Jun. 11, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE NVD-CWE-noinfo
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.30 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.7 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10 up to (excluding) 6.6.142 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.92
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/531c537b8fb620beabccfb1594e8d43cbebbb87a Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/6a3af482188f6db4186d1605f64d911d7330abb3 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/8143a224785ceaf2b0856e08d4498916f38228fb Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/b74ad20198652b6b39a761c277ba65ae82b1e107 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/b7b9a461569734d33d3259d58d2507adfac107ed Types: Patch
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jun. 01, 2026

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/531c537b8fb620beabccfb1594e8d43cbebbb87a
    Added Reference https://git.kernel.org/stable/c/6a3af482188f6db4186d1605f64d911d7330abb3
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    May. 28, 2026

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: free sk if last When an ADD_ADDR is retransmitted, the sk is held in sk_reset_timer(), and released at the end. If at that moment, it was the last reference being held, the sk would not be freed. sock_put() should then be called instead of __sock_put(). But that's not enough: if it is the last reference, sock_put() will call sk_free(), which will end up calling sk_stop_timer_sync() on the same timer, and waiting indefinitely to finish. So it is needed to mark that the timer is done at the end of the timer handler when it has not been rescheduled, not to call sk_stop_timer_sync() on "itself".
    Added Reference https://git.kernel.org/stable/c/8143a224785ceaf2b0856e08d4498916f38228fb
    Added Reference https://git.kernel.org/stable/c/b74ad20198652b6b39a761c277ba65ae82b1e107
    Added Reference https://git.kernel.org/stable/c/b7b9a461569734d33d3259d58d2507adfac107ed
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.